Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

SAX logging

Specifying the SAX log entry type turns on logging of the following different types of messages, as the SAX parser executes, as shown in Table 6–5.

Table 6–5: Sax parser logging messages

When logging occurs	What is logged
OpenEdge initializes the SAX parser.	Initialize parser
OpenEdge finishes using the parser.	Exiting parser
OpenEdge finds a callback to run.	Callback internal-routine-name found in super procedure — OR — Callback internal-routine-name found
OpenEdge does not find a callback to run.	Callback internal-routine-name not found
For each parameter in a callback, the log message includes the following, depending on the parameter type: CHARACTER, MEMPTR (which contains a string), or INTEGER. If CHARACTER parameter is empty. HANDLE.	parameter parameter-number: value   parameter parameter-number: <null> parameter parameter-number: <valid-handle>

The following example shows log entries for the SAX component at logging level (BASIC) 2 (with headers suppressed):

1 4GL -- Log entry types activated:SAX 2 4GL SAX    Initialize parser 2 4GL SAX    Callback StartDocument not found 2 4GL SAX    Callback StartElement found 2 4GL SAX        parameter 1: <null> 2 4GL SAX        parameter 2: custorders 2 4GL SAX        parameter 3: custorders 2 4GL SAX        parameter 4: <valid handle> 2 4GL SAX    Callback Characters found 2 4GL SAX        parameter 1: 2 4GL SAX        parameter 2: 1 2 4GL SAX    Callback EndElement found 2 4GL SAX        parameter 1: <null> 2 4GL SAX        parameter 2: city 2 4GL SAX        parameter 3: city 2 4GL SAX    Callback EndDocument not found 2 4GL SAX    Exiting parser